618.3.4 Start messaging background process[//]

This option allows you to start up the messaging processing job. This processes the reservations, searching through the defined lists for each pickup location, moving reservations through the lists as necessary. After choosing this option an input form will be displayed:

You should enter a time at which the processing should end e.g. “22:00”. In addition, enter a value in minutes for the successive passes (to how often the job should run to check through the reservations).

Note

The processing is quite intensive so, for performance reasons, you should run this as infrequently as possible but commensurate with the sorts of timeout periods you have chosen for your service points.

For example, if you typically allow each service point 3 days in which to respond to a “message”, then it is probably inappropriate to run the background process every 5 minutes!.

After clicking OK, you are then offered the standard screen for submitting a “process”. Normally you would schedule this in memory. However, you CAN run the process online or in batch. In this case, the processing will run ONCE only, rather than looping indefinitely; and this option would normally be used for testing.

618.3.5 Route exhausted actions[//]

It is possible to assign specific actions to “messages” appearing in the “route exhausted” display (AFO 418). This allows you to define specific actions or statuses to be assigned to messages appearing in the list.

After choosing this option an overview screen will be displayed:

Options on the screen

New action code: Select this option to create a new code. See section 618.3.5.1.

Delete action code: Select a code and then this option to delete it. The system wil prompt for confirmation.

Modify action code: Select a code and then this option to modify it.

618.3.5.1 New code[//]

New action code: Select this option to create a new code. An input form will be displayed:

Fields on the screen

Action code: code to be assigned to this action.

Description: A description of the code.

Display icon: An icon which will appear against the messages in the route exhausted display, when this action is set against the message. This is a drop-down field – the system offers you a choice of about 16 different icons.

Hide message: This tells the system to remove the message from the display when this action is set. For example, when applying a status of “completed”, you might decide to remove this message from the display completely. You should note that the message itself is not deleted from the system – only hidden; by reversing the “hide message” setting, such messages will be made visible again.